Open
Conversation
Contributor
|
Filename needs to be corrected, from |
TallTed
reviewed
Apr 10, 2026
| ### Demos | ||
|
|
||
| * eP: Since we aren't seeing any new demos, can we assume that there isn't any implementation work happening? | ||
| * eP: Who would like to do short demos in upcoming weeks? I can do another short one of sai-js eg. access grants. |
Contributor
There was a problem hiding this comment.
Suggested change
| * eP: Who would like to do short demos in upcoming weeks? I can do another short one of sai-js eg. access grants. | |
| * eP: Who would like to do short demos in upcoming weeks? I can do another short one of `sai-js`, e.g., access grants. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+88
to
+89
| * ...: Some WGs already settled e.g. EDMA who are willing to invest time into Solid. | ||
| * ...: E.g. Gov leads: Will look across different governments (multinationally) for diversity of use cases across the world. |
Contributor
There was a problem hiding this comment.
Suggested change
| * ...: Some WGs already settled e.g. EDMA who are willing to invest time into Solid. | |
| * ...: E.g. Gov leads: Will look across different governments (multinationally) for diversity of use cases across the world. | |
| * ...: Some WGs already settled, e.g., EDMA, who are willing to invest time into Solid. | |
| * ...: E.g., Gov leads: Will look across different governments (multinationally) for diversity of use cases across the world. |
TallTed
reviewed
Apr 10, 2026
| * ...: Some WGs already settled e.g. EDMA who are willing to invest time into Solid. | ||
| * ...: E.g. Gov leads: Will look across different governments (multinationally) for diversity of use cases across the world. | ||
| * ...: Will ask WGs for output as spreadsheet of priorities. Then Feedback Panel will prioritise across WGs. | ||
| * ...: Panel comprised of persona group leads. Also members from adisory committee. Also W3C rep who know global context and are well placed to communicate outcomes widely. |
Contributor
There was a problem hiding this comment.
Suggested change
| * ...: Panel comprised of persona group leads. Also members from adisory committee. Also W3C rep who know global context and are well placed to communicate outcomes widely. | |
| * ...: Panel comprised of persona group leads. Also members from advisory committee. Also W3C rep(s) who know global context and are well placed to communicate outcomes widely. |
TallTed
reviewed
Apr 10, 2026
| * JW: N3 | ||
| * JW: Inclusion of other documents | ||
|
|
||
| * JW: thank sarvin for feedback, and that CB is working with him on this, though he is unable to join today. |
Contributor
There was a problem hiding this comment.
Suggested change
| * JW: thank sarvin for feedback, and that CB is working with him on this, though he is unable to join today. | |
| * JW: thank Sarven for feedback, and that CB is working with him on this, though he is unable to join today. |
TallTed
reviewed
Apr 10, 2026
| * JW: Inclusion of other documents | ||
|
|
||
| * JW: thank sarvin for feedback, and that CB is working with him on this, though he is unable to join today. | ||
| * JW: shares screen to go over the pull request (listed above) - At present we have an abstract talking about what Solid26 is: Nonormative document, a collection of exsiting works. Key thing being servers should comply to WAC, may also support ACP (as per the survey conducted last week), it points to a snapshot of WAC which may be updated if Sarven puts up a new version before Solid26. Also includes work on guidance by Samu |
Contributor
There was a problem hiding this comment.
Suggested change
| * JW: shares screen to go over the pull request (listed above) - At present we have an abstract talking about what Solid26 is: Nonormative document, a collection of exsiting works. Key thing being servers should comply to WAC, may also support ACP (as per the survey conducted last week), it points to a snapshot of WAC which may be updated if Sarven puts up a new version before Solid26. Also includes work on guidance by Samu | |
| * JW: shares screen to go over the pull request (listed above) - At present we have an abstract talking about what Solid26 is: Non-normative document, a collection of existing works. Key thing being servers should comply to WAC, may also support ACP (as per the survey conducted last week), it points to a snapshot of WAC which may be updated if Sarven puts up a new version before Solid26. Also includes work on guidance by Samu. |
TallTed
reviewed
Apr 10, 2026
|
|
||
| * JW: thank sarvin for feedback, and that CB is working with him on this, though he is unable to join today. | ||
| * JW: shares screen to go over the pull request (listed above) - At present we have an abstract talking about what Solid26 is: Nonormative document, a collection of exsiting works. Key thing being servers should comply to WAC, may also support ACP (as per the survey conducted last week), it points to a snapshot of WAC which may be updated if Sarven puts up a new version before Solid26. Also includes work on guidance by Samu | ||
| * SL: the suammry is: these are the things he knows an implementos would need to knwo to work WebID - everything thatc omes to mind when thinking about building with WebID in the Solid ecosystem. |
Contributor
There was a problem hiding this comment.
Suggested change
| * SL: the suammry is: these are the things he knows an implementos would need to knwo to work WebID - everything thatc omes to mind when thinking about building with WebID in the Solid ecosystem. | |
| * SL: the summary is: these are the things he knows an implementor would need to know to work WebID — everything that comes to mind when thinking about building with WebID in the Solid ecosystem. |
TallTed
reviewed
Apr 10, 2026
| * JW: shares screen to go over the pull request (listed above) - At present we have an abstract talking about what Solid26 is: Nonormative document, a collection of exsiting works. Key thing being servers should comply to WAC, may also support ACP (as per the survey conducted last week), it points to a snapshot of WAC which may be updated if Sarven puts up a new version before Solid26. Also includes work on guidance by Samu | ||
| * SL: the suammry is: these are the things he knows an implementos would need to knwo to work WebID - everything thatc omes to mind when thinking about building with WebID in the Solid ecosystem. | ||
| * EP: how do you see the dif between the webid profile draft, and this? | ||
| * SL: i dont think i can summarize this simply, in this doc Samu has tried to skip over things seen as being contentious, and focus on things we agree are useful. |
Contributor
There was a problem hiding this comment.
Suggested change
| * SL: i dont think i can summarize this simply, in this doc Samu has tried to skip over things seen as being contentious, and focus on things we agree are useful. | |
| * SL: i don't think i can summarize this simply. in this doc, Samu has tried to skip over things seen as being contentious, and focus on things we agree are useful. |
TallTed
reviewed
Apr 10, 2026
| * SL: the suammry is: these are the things he knows an implementos would need to knwo to work WebID - everything thatc omes to mind when thinking about building with WebID in the Solid ecosystem. | ||
| * EP: how do you see the dif between the webid profile draft, and this? | ||
| * SL: i dont think i can summarize this simply, in this doc Samu has tried to skip over things seen as being contentious, and focus on things we agree are useful. | ||
| * AB: I notice you indicate a need to use M3Patch, but is that required to all servers |
Contributor
There was a problem hiding this comment.
Suggested change
| * AB: I notice you indicate a need to use M3Patch, but is that required to all servers | |
| * AB: I notice you indicate a need to use M3Patch, but is that required of all servers? |
TallTed
reviewed
Apr 10, 2026
| * EP: how do you see the dif between the webid profile draft, and this? | ||
| * SL: i dont think i can summarize this simply, in this doc Samu has tried to skip over things seen as being contentious, and focus on things we agree are useful. | ||
| * AB: I notice you indicate a need to use M3Patch, but is that required to all servers | ||
| * JW: as it sitands it is not required in servers, meaning clients should not expect to see it. Sarven asked why we left it out, my answer (connected on a conversation with TimBL) is that not all servers implement M3Patch - i sudgested we try and do a similar data gathering exercise to what we did with Wac/ACP, and im inclined to hold that qiuestion to later in the week so we can roll it in with more questions we would ahve for server implemntors. |
Contributor
There was a problem hiding this comment.
Suggested change
| * JW: as it sitands it is not required in servers, meaning clients should not expect to see it. Sarven asked why we left it out, my answer (connected on a conversation with TimBL) is that not all servers implement M3Patch - i sudgested we try and do a similar data gathering exercise to what we did with Wac/ACP, and im inclined to hold that qiuestion to later in the week so we can roll it in with more questions we would ahve for server implemntors. | |
| * JW: as it stands, it is not required in servers, meaning clients should not expect to see it. Sarven asked why we left it out. My answer (connected to a conversation with TimBL) is that not all servers implement M3Patch — I suggested we try and do a similar data gathering exercise as what we did with WAC/ACP, and I'm inclined to hold that question to later in the week, so we can roll it in with more questions we would have for server implementors. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+128
to
+130
| * AB: yes but there were other methods to use, most servers are using Sparkle updates | ||
| * JW: yes, though sparkle updates are not in the current specs - so in the current guide there is not patch recomendation. | ||
| * EP: ill take the opportunity to put Erich on the spot and ask how patching is done in LWF |
Contributor
There was a problem hiding this comment.
Suggested change
| * AB: yes but there were other methods to use, most servers are using Sparkle updates | |
| * JW: yes, though sparkle updates are not in the current specs - so in the current guide there is not patch recomendation. | |
| * EP: ill take the opportunity to put Erich on the spot and ask how patching is done in LWF | |
| * AB: Yes, but there were other methods to use. Most servers are using SPARQL Update. | |
| * JW: Yes, though SPARQL Update is not in the current specs — so in the current guide, there is no patch recommendation. | |
| * EP: I'll take the opportunity to put Erich on the spot, and ask how patching is done in LWS. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+131
to
+133
| * EB: its defined in JSON (from EB in chat: and by PATCH for json, I mean specifically, JSON Merge Patch RFC7386 ) | ||
| * EP: i woul;d sudgets we dont try to get patch right in this pull request, we can adress that later int he week (tackle these things one at a time) | ||
| * JW: i think the discussion to have in this group is the genral design priocipal of this implemntors guide: so far the idea has been to be very minimal, my sudgestion is that for Solid26 we let people see little at first and discover the rest of the specs as they go on. Meaning anything that are not extremely stable across servers and clients in the Solid ecosystem we leave out of this document. |
Contributor
There was a problem hiding this comment.
Suggested change
| * EB: its defined in JSON (from EB in chat: and by PATCH for json, I mean specifically, JSON Merge Patch RFC7386 ) | |
| * EP: i woul;d sudgets we dont try to get patch right in this pull request, we can adress that later int he week (tackle these things one at a time) | |
| * JW: i think the discussion to have in this group is the genral design priocipal of this implemntors guide: so far the idea has been to be very minimal, my sudgestion is that for Solid26 we let people see little at first and discover the rest of the specs as they go on. Meaning anything that are not extremely stable across servers and clients in the Solid ecosystem we leave out of this document. | |
| * EB: It's defined in JSON _(from EB in chat: and by PATCH for JSON, I mean specifically, JSON Merge Patch RFC7386)_ | |
| * EP: I would suggest we don't try to get patch right in this pull request. We can address that later in the week. (Tackle these things one at a time.) | |
| * JW: I think the discussion to have in this group is the general design principal of this implementor's guide. So far, the idea has been to be very minimal; my suggestion is that, for Solid26, we let people see little at first and discover the rest of the specs as they go on. Meaning anything that is not extremely stable across servers and clients in the Solid ecosystem, we leave out of this document. |
TallTed
reviewed
Apr 10, 2026
| * EP: i woul;d sudgets we dont try to get patch right in this pull request, we can adress that later int he week (tackle these things one at a time) | ||
| * JW: i think the discussion to have in this group is the genral design priocipal of this implemntors guide: so far the idea has been to be very minimal, my sudgestion is that for Solid26 we let people see little at first and discover the rest of the specs as they go on. Meaning anything that are not extremely stable across servers and clients in the Solid ecosystem we leave out of this document. | ||
|
|
||
| Discussion with Michal - on put requests decvided to be taken in writing due to specificity. |
Contributor
There was a problem hiding this comment.
I'm not sure about this text. Might need some words to change to accurately reflect conversation.
Suggested change
| Discussion with Michal - on put requests decvided to be taken in writing due to specificity. | |
| Discussion with Michal — on put requests decided to be taken in writing due to specificity. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+137
to
+139
| * EP: sudgests we get this pull request done soon so we have a basis to make pull requests on over the next few weeks. as we dont ahve much time to do all this in meetings. | ||
| * EP: what is the future of the Solid26 repo? | ||
| * JW: I see this markdown doc as a very shorlived thing to help ppeople who are not in CG calls catch up on what Solid26 is - we are cuirrently working on full Solid26 webpages (Precious is on it). there will be 2 pages: one for fully leigh people, giving them info and inviting them to messege Roberto for rounting. the second is for impklentors worki g in Solid so new people coming in to the ecosystme know what we think about eh future of Solid (igrate to LWS). again this will be an opinionated docuemnt since we dont have consensus. |
Contributor
There was a problem hiding this comment.
Suggested change
| * EP: sudgests we get this pull request done soon so we have a basis to make pull requests on over the next few weeks. as we dont ahve much time to do all this in meetings. | |
| * EP: what is the future of the Solid26 repo? | |
| * JW: I see this markdown doc as a very shorlived thing to help ppeople who are not in CG calls catch up on what Solid26 is - we are cuirrently working on full Solid26 webpages (Precious is on it). there will be 2 pages: one for fully leigh people, giving them info and inviting them to messege Roberto for rounting. the second is for impklentors worki g in Solid so new people coming in to the ecosystme know what we think about eh future of Solid (igrate to LWS). again this will be an opinionated docuemnt since we dont have consensus. | |
| * EP: Suggest we get this pull request done soon so we have a base to make pull requests on over the next few weeks, as we don't have much time to do all this in meetings. | |
| * EP: What is the future of the Solid26 repo? | |
| * JW: I see this markdown doc as a very short-lived thing, to help people who are not in CG calls catch up on what Solid26 is. We are currently working on full Solid26 webpages (Precious is on it). There will be 2 pages: one for fully lay-people, giving them info and inviting them to message Roberto for rounting(?). The second is for implentors working in Solid so new people coming in to the ecosystem know what we think about the future of Solid (migrate to LWS). Again, this will be an opinionated document since we don't have consensus. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+140
to
+141
| * EP: To me its importnat we connect Solid26 pages to what Roberto presented in terms of persona groups, and its important that Soli26 helps the CG build capacity (new people) to help improve Solid. | ||
| * JW: One thing im hoping the prioritising can help with is also finding the things that need the most work, and focus our energy limited as it is. |
Contributor
There was a problem hiding this comment.
Suggested change
| * EP: To me its importnat we connect Solid26 pages to what Roberto presented in terms of persona groups, and its important that Soli26 helps the CG build capacity (new people) to help improve Solid. | |
| * JW: One thing im hoping the prioritising can help with is also finding the things that need the most work, and focus our energy limited as it is. | |
| * EP: To me, it's important that we connect Solid26 pages to what Roberto presented in terms of persona groups, and it's important that Solid26 helps the CG build capacity (new people) to help improve Solid. | |
| * JW: One thing im hoping the prioritising can also help with is finding the things that need the most work, and focusing our energy, limited as it is. |
TallTed
reviewed
Apr 10, 2026
| ### Solid Shapes | ||
| - https://github.com/solid/shapes | ||
|
|
||
| * JW: Shapes repo content overview (tgra) |
Contributor
There was a problem hiding this comment.
Suggested change
| * JW: Shapes repo content overview (tgra) | |
| * JW: Shapes repo content overview (https://github.com/tgra/) |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+153
to
+154
| * TG: The shape repo currently holds shapes extracted from SolidOS. The goal of the repository is to support interoperablity across semantic domains. In addition to the shapes that are there, there are guidelines for how people can contribute shapes. | ||
| * JW: Goal is to enable interop within Solid ecosystem as it stands today. We don't have huge number of apps but hope this number can grow. In short term we can provide human consensus way to collect what apps are using. You capture the data model within this repo by creating a PR, this way people can see what others are using. When you build a new app you try to reuse the shape. It is an experiment, we don't know if people will adopt it, what is the right incentive. In email thread Virginia have asked what is the gov process. Proposal is that while it is small we get 10-15 shapes contributed and ODI governs it. Should it proved to be a success and CG wants to take ownership we can talk about it. |
Contributor
There was a problem hiding this comment.
Suggested change
| * TG: The shape repo currently holds shapes extracted from SolidOS. The goal of the repository is to support interoperablity across semantic domains. In addition to the shapes that are there, there are guidelines for how people can contribute shapes. | |
| * JW: Goal is to enable interop within Solid ecosystem as it stands today. We don't have huge number of apps but hope this number can grow. In short term we can provide human consensus way to collect what apps are using. You capture the data model within this repo by creating a PR, this way people can see what others are using. When you build a new app you try to reuse the shape. It is an experiment, we don't know if people will adopt it, what is the right incentive. In email thread Virginia have asked what is the gov process. Proposal is that while it is small we get 10-15 shapes contributed and ODI governs it. Should it proved to be a success and CG wants to take ownership we can talk about it. | |
| * TG: The shape repo currently holds shapes extracted from SolidOS. The goal of the repository is to support interoperablity across semantic domains. In addition to the shapes that are there, there are guidelines for how people can contribute shapes. | |
| * JW: The goal is to enable interop within the Solid ecosystem as it stands today. We don't have a huge number of apps but hope this number can grow. In the short term, we can provide a human consensus way to collect what apps are using. You capture the data model within this repo by creating a PR; this way, people can see what others are using. When you build a new app, you try to reuse shapes. It is an experiment; we don't know if people will adopt it, nor what is the right incentive. In an email thread, Virginia has asked what is the governance process. Proposal is that while it is small, we get 10-15 shapes contributed, and ODI governs it. Should it prove to be a success and the CG wants to take ownership, we can talk about it. |
TallTed
reviewed
Apr 10, 2026
| * JW: Shapes repo content overview (tgra) | ||
| * TG: The shape repo currently holds shapes extracted from SolidOS. The goal of the repository is to support interoperablity across semantic domains. In addition to the shapes that are there, there are guidelines for how people can contribute shapes. | ||
| * JW: Goal is to enable interop within Solid ecosystem as it stands today. We don't have huge number of apps but hope this number can grow. In short term we can provide human consensus way to collect what apps are using. You capture the data model within this repo by creating a PR, this way people can see what others are using. When you build a new app you try to reuse the shape. It is an experiment, we don't know if people will adopt it, what is the right incentive. In email thread Virginia have asked what is the gov process. Proposal is that while it is small we get 10-15 shapes contributed and ODI governs it. Should it proved to be a success and CG wants to take ownership we can talk about it. | ||
| * eP: I think it is important that job is getting done. CG had a plenty of oportunity to do it. |
Contributor
There was a problem hiding this comment.
Suggested change
| * eP: I think it is important that job is getting done. CG had a plenty of oportunity to do it. | |
| * eP: I think it is important that this job is getting done. CG had a plenty of opportunity to do it. |
TallTed
reviewed
Apr 10, 2026
Comment on lines
+160
to
+161
| * TG: The requirement for chat channel to have new file each day conforming to certain pattern. This would require variables and how to represent it in SHACL. The use of templating came forward as an idea. I did some documentation, there's also idea of using Hydra templates. | ||
| * JW: There is a conversation a couple of steps back. It is another way of trying to help interop. The proposal is a way of defining within a shapes repo a fixed path within a storage. For example volunteering can be in `/volunteering/profiles`. For example the way chat spec requires a path today. |
Contributor
There was a problem hiding this comment.
Suggested change
| * TG: The requirement for chat channel to have new file each day conforming to certain pattern. This would require variables and how to represent it in SHACL. The use of templating came forward as an idea. I did some documentation, there's also idea of using Hydra templates. | |
| * JW: There is a conversation a couple of steps back. It is another way of trying to help interop. The proposal is a way of defining within a shapes repo a fixed path within a storage. For example volunteering can be in `/volunteering/profiles`. For example the way chat spec requires a path today. | |
| * TG: The requirement for a chat channel to have a new file each day conforming to a certain pattern. This would require variables and how to represent it in SHACL. The use of templating came forward as an idea. I did some documentation. There's also idea of using Hydra templates. | |
| * JW: There is a conversation a couple of steps back. It is another way of trying to help interop. The proposal is a way of defining within a shapes repo a fixed path within a storage. For example, volunteering might be in `/volunteering/profiles`. For example, the way chat spec requires a path today. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.